Take published missions into your own agent workflow - #15
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Contributors can now take a published mission from its shared room into an agent they already use. A reviewable brief and matching JSON snapshot include the mission source, existing API references, a bounded planning step and links back to the selected mission's participation and evidence forms.
The export reads only allowlisted public fields and grants no permissions. Room changes and unavailable missions clear the previous brief; late responses and clipboard failures cannot restore stale context. Public reference text remains inside its JSON boundary, and downloads are revoked on navigation.
Validation: repository and machine-contract checks pass, with eight controller tests covering private-field isolation, hostile reference text, JSON round-trips, response races and lifecycle cleanup. Browser checks cover clipboard equality, the mission-preserving Workshop return path, keyboard navigation, desktop and 320/390-pixel layouts. Both independent builds match byte for byte.